Dynomotion

Group: DynoMotion Message: 6085 From: schnauzer61 Date: 11/14/2012
Subject: Loss of configuration
Having slowly got my KFlop/KAnalogue working beautifully (I'm a bit limited for time) and enjoying the difference from Mach3, I finally found time to get spindle on/off and EStop working.

This seemed to go well, and tested fine.

The next time I restarted everything, KMotion.exe complained that it could not read persist.ini. The file is there, but empty.

KMotionCNC starts without complaint, but has lost all configuration, including the look of the window, user buttons, tool & trajectory setup etc..

I've looked in the doco and forum, but can't find anything useful.

I presume that my basic axis configuration is still in the flash memory but I'm reluctant to try too much until I have a bit more information. I definitely don't want to reinvent everything.

1. Is persist.ini the only configuration I've lost? What other config files should there be in the Data directory and what do they contain?

2. Can you suggest a reason that this might have happened? I'm pretty sure that the new C programs for spindle control & EStop must be irrelevant - I haven't had any trouble before. The only real change is that the EStop program is constantly running in thread 7.

Thanks

John
Group: DynoMotion Message: 6086 From: Tom Kerekes Date: 11/14/2012
Subject: Re: Loss of configuration
Hi John,

Sorry to hear that.  I assume you don't have any backup?  The Data directory contains a number of files for the various KMotion and KMotionCNC screens.  persist.ini is the higher level for KMotion.exe,  persistCNC.ini is the higher level for KMotionCNC.  The others are for the individual screens.  It seems especially odd that more than one file for more than one application is lost.

We don't recommend that you Flash settings into the board.  It is better to just let a C program configure them on every initialization.  It is just more confusing and there is no real advantage unless you need to run stand-alone without a PC.

But if you did Flash the settings or if you have a C program to configure the board then you can upload the settings from the board into the KMotion.exe screens. See:

http://dynomotion.com/Help/FlashHelp/Parameters/index.html

I can't see how the EStop program could be related.

Regards
TK

Group: DynoMotion Message: 6087 From: schnauzer61 Date: 11/14/2012
Subject: Re: Loss of configuration
I've since looked further. Bode.txt, GFiles.txt, GFilesCNC.txt, persist.ini & persistCNC.ini all exist but are empty.

I can only imagine that something went wrong while they were being written to (during shutdown?). Nothing else seems wrong with the PC or anything else - just those configurations.

I was just thinking that I should do a backup, but had not quite got there. I should know better.

My KFlop settings are in fact set by a C program - that's what I meant because I assume that the program is still in the KFlop memory.

It looks as if I'll need to reinstall the KFlop software to give me a valid starting point for rebuilding. (Keeping the Data directory of course, and taking a backup when I'm finished!)

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi John,
>
> Sorry to hear that.  I assume you don't have any backup?  The Data directory contains a number of files for the various KMotion and KMotionCNC screens.  persist.ini is the higher level for KMotion.exe,  persistCNC.ini is the higher level for KMotionCNC.  The others are for the individual screens.  It seems especially odd that more than one file for more than one application is lost.
>
> We don't recommend that you Flash settings into the board.  It is better to just let a C program configure them on every initialization.  It is just more confusing and there is no real advantage unless you need to run stand-alone without a PC.
>
> But if you did Flash the settings or if you have a C program to configure the board then you can upload the settings from the board into the KMotion.exe screens. See:
>
> http://dynomotion.com/Help/FlashHelp/Parameters/index.html
>
>
> I can't see how the EStop program could be related.
>
> Regards
> TK
>
>
> ________________________________
> From: schnauzer61 <schnauzer61@...>
> To: DynoMotion@yahoogroups.com
> Sent: Wednesday, November 14, 2012 1:28 PM
> Subject: [DynoMotion] Loss of configuration
>
>
>  
> Having slowly got my KFlop/KAnalogue working beautifully (I'm a bit limited for time) and enjoying the difference from Mach3, I finally found time to get spindle on/off and EStop working.
>
> This seemed to go well, and tested fine.
>
> The next time I restarted everything, KMotion.exe complained that it could not read persist.ini. The file is there, but empty.
>
> KMotionCNC starts without complaint, but has lost all configuration, including the look of the window, user buttons, tool & trajectory setup etc..
>
> I've looked in the doco and forum, but can't find anything useful.
>
> I presume that my basic axis configuration is still in the flash memory but I'm reluctant to try too much until I have a bit more information. I definitely don't want to reinvent everything.
>
> 1. Is persist.ini the only configuration I've lost? What other config files should there be in the Data directory and what do they contain?
>
> 2. Can you suggest a reason that this might have happened? I'm pretty sure that the new C programs for spindle control & EStop must be irrelevant - I haven't had any trouble before. The only real change is that the EStop program is constantly running in thread 7.
>
> Thanks
>
> John
>